Support "no init access" feature of Kvaser interfaces #1955
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I would recommend adding a test for it in test/test_kvaser.py I can look into it |
Contributor
Author
Agreed, thanks for pointing me to it. I've added a test case dedicated to this single keyword argument. |
fl0gee
force-pushed
the
feature/no-init-access-support-for-kvaser
branch
from
dccbb22 to
2045ce7
Compare
zariiii9003
approved these changes
Jul 21, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The Kvaser CANlib SDK supports opening a channel without initializing it with defined bit rate, see:
https://kvaser.com/canlib-webhelp/canlib_8h.htm#a1d7dee5873b91fc267239dfaedf977df
This PR is adding a keyword argument to the
KvaserBusfor supporting this functionality.